Flash the right file.
Send the right data.

01 / BEFORE YOU START

Confirm the car, file and equipment.

• Check the exact vehicle, Accessport compatibility and the tune file’s intended hardware and fuel.
• Have a USB data cable, a computer with COBB Accessport Manager ↗, the OBD-II cable and appropriate battery support ready.
• For a legacy/pre–Green Speed setup, tell me your current software and kit details before making updates or changing the configuration. Follow the manufacturer’s applicable support instructions.
• Resolve known faults and confirm the wideband recording plan where required. Review wideband requirements.

This guide covers file handling and logger setup. It does not authorize a full-load test. Set up the device while stationary, secure cables away from the controls, and use only the operating conditions I request.

02 / COMPUTER TO ACCESSPORT

How to put a tune file on your Accessport.

1. Save the file I sent to your computer. Keep its revision name intact.
2. Connect the Accessport by USB and open Accessport Manager. Connect in the application if it does not connect automatically.
3. In the file-management screen, import the map file to the handheld. Wait for the transfer to finish.
4. Eject/disconnect through the application before unplugging.

Transferring is not flashing. The file is now on the handheld; the car’s ECU has not yet been changed.

Reference: COBB Accessport Manager manual ↗.

03 / ACCESSPORT TO ECU

How to flash a tune with an Accessport.

1. Prepare power. Park, switch off accessories and connect suitable battery support. COBB specifies a 10–20 amp charger for most install/uninstall procedures, rather than a tender or jump pack. Follow the instructions for your application.
2. Connect securely. Attach the OBD-II cable. Put the ignition in ON with the engine stopped, following the device prompts.
3. Select the operation. For a paired device, use Tune → Change Map and the reflash option I specify. First-time pairing uses Install; do not uninstall for an ordinary revision.
4. Confirm the file. Check the revision, car, hardware and fuel before starting.
5. Let programming finish. Leave power and cables undisturbed. Complete every ignition-cycle prompt before starting the engine.

Older Subaru applications may require test-mode and initialization connectors. Follow the exact vehicle/Accessport manual; these are not universal steps for every Subaru. Disconnect any required programming connectors as directed before operating the car.

After flashing, confirm the current map and follow my startup instructions. A realtime change, where offered, is not the same operation as a full reflash. If uncertain, ask before choosing.

References: COBB quick start ↗, Subaru manual ↗ and Porsche manual ↗. On-screen directions for your supported vehicle take priority over generic menu examples.

04 / RECORDING DATA

How to datalog with an Accessport V3.

1. While parked, open Gauges → Setup → Configure Datalogging.
2. Enable the channels from the agreed list. Save the selection. The visible dashboard gauges are separate from the recording list.
3. Return to Gauges. Press the center OK button to begin recording; confirm the logging indicator is active. Press OK again to stop.
4. Export a short stationary test CSV first and verify its column headers before collecting the requested session.

Keep the channel list focused. If the device warns about too many monitors or the sample rate is poor, send me your selection so we can trim it. Do not drop required fueling or knock data at random.

Start with the idle or light-load check I request. Full-load work requires separate instructions and a suitable dyno or controlled closed course. Do not operate the logger or watch its screen while driving. Stop for misfires, unexpected boost, abnormal temperature, warning lights, fuel smell or other unsafe behavior.

Reference: COBB’s datalogging walkthrough ↗. Menu wording and available monitors vary by firmware and vehicle.

05 / SUBARU PARAMETER LISTS

Start with the core channels.
Then add your platform’s channels.

These are customer setup references, not universal importable presets. Use the channels available on your ECU/ROM and the final list I supply. A missing sensor cannot be added by selecting a similar name. Do not enable every item on this page in one log.

The ECU’s front-sensor channel is not automatically a substitute for the external wideband measurement required for older-car fueling work. Avoid universal “good/bad” thresholds from a different engine family.

COBB Subaru monitor definitions and availability ↗ · Keith’s Subaru parameter reference (PDF).

EJ / 2002–2014 WRX & 2004–2021 STI

What should I log on an EJ WRX or STI?

Keep the core channels above, then confirm these additions for your car:

• Injector pulse width and/or injector duty cycle.
• Commanded fuel, often labelled Comm Fuel Final where supported.
• Wastegate Duty and the available boost target/error channel.
• External wideband AFR or lambda using an approved, time-aligned recording method.
• Fuel pressure only with a supported sensor and input; do not assume every EJ has factory fuel-pressure logging.
• Cam-control channels when requested and available for your engine.

For EJ remote tuning, an external wideband with an approved recording method is required. The factory oxygen-sensor channel or a gauge video is not a substitute. Include any iWire or pre–Green Speed logging setup and legacy flex-fuel module details when asking for your list.

EJ WRX & STI tuning requirements →

FA20DIT / 2015–2021 WRX

What should I log on a 2015–2021 WRX?

Use the core Subaru channels plus the FA20 items requested for your revision:

• Actual fuel-rail pressure and target pressure, commonly Fuel Pressure and Fuel Pressure Target.
• Intake Temp Manifold and Oil Temp where available.
• Injector duty/pulse width and direct-injection timing channels as requested.
• Intake and exhaust AVCS channels for the available left/right banks when requested.
• Wastegate Duty and boost target/error for the installed calibration.

For 2015–2017 remote fueling work, confirm the external wideband recording plan. For 2018–2021 cars, I review the measurement requirements individually. The STI from these years uses the EJ section, not this FA20 list.

FA20 WRX tuning requirements →

FA24DIT / 2022+ WRX

What should I log on a 2022+ WRX?

Start with the core Subaru channels, then confirm the FA24-specific selection:

• Actual and target fuel-rail pressure.
• Intake Temp Manifold, Oil Temp and requested direct-injection channels.
• MAF Freq and/or corrected airflow as specified for your ROM.
• Electronic wastegate channels such as Wastegate Pos Actual and Wastegate Pos Comm Final, where exposed, instead of assuming an older duty-cycle preset applies.
• Requested torque and the available boost target/error channels when requested.

Names, supported channels and interpretation can differ from the FA20. Send a short test CSV before assuming an older WRX preset is complete.

FA24 WRX tuning requirements →

WIDEBAND & FLEX-FUEL LOGGING

Include the data your hardware can actually record.

For an approved flex-fuel setup, include ethanol content and the requested fuel-pressure/flex channels supported by your calibration. Tell me the sensor, controller, kit generation and fuel blend. Do not change blends during the process without agreement.

For an external wideband, confirm AFR versus lambda, the fuel scale, controller and sensor, connection type and time alignment with the ECU log. If it records separately, send both original files with enough context to align them.

I support compatible pre–Green Speed iWire arrangements and legacy flex-fuel kits, including Delicious Tuning. The logging path must match the actual software; a legacy input is not automatically available in a current Accessport log. Review legacy flex-fuel compatibility →

PORSCHE / SUPPORTED ACCESSPORT APPLICATIONS

Which parameters should Porsche owners log?

Send the model, year, engine, Accessport part number and current map first. Porsche channel sets differ between generations and engines, so a Subaru preset does not apply.

Unless I supply a custom list, COBB’s default datalog selection is the starting point. Keep RPM, accelerator/throttle position, load and barometric pressure; include boost for turbocharged applications. I may request additional fueling, temperature and cylinder-specific ignition data for the exact engine.

Only add PDK channels when needed for the agreed diagnostic work and supported by your device; adding transmission channels can reduce the engine logging rate. No single list here is presented as covering every Porsche ECU.

COBB’s Porsche platform logging reference ↗ · Porsche tuning with Keith →

06 / EXPORT & SEND

How to get datalogs off the Accessport.

1. Connect the handheld to the computer and open Accessport Manager.
2. Filter the file list to datalogs. Select the relevant recording and save it to your computer.
3. Keep the original CSV, including column names, units and timestamps. Make a backup before deleting anything from the device.
4. For an active tuning order, open Messages, logs & revision history on your private order page. Upload the file with the tune revision, fuel, requested test and symptoms. See the order-page guide for help. Do not substitute gauge screenshots or a video.

Suggested filename: WRX_R03_warm-idle_2026-10-30.csv. Include any change since the previous log and wait for review before advancing to another test.

The device’s storage is finite; export promptly so an old recording is not overwritten.

Reference: COBB file-transfer instructions ↗.

HELP WITH YOUR SETUP

Need the right list for your car?

Send the year, model, engine, tuning device, parts, fuel and current tune history. I can confirm the recording requirements before you order equipment or a tuning service.