Hondata KPro and FlashPro basics: connect, calibrations and logs

• KPro is a board inside a compatible factory ECU. The calibration lives in that ECU, and KManager reads or writes it over USB. FlashPro is an external device. It stores up to two calibrations, called primary and secondary, and it can write one to the ECU from its own buttons. That is a different chain from KPro.
• The laptop is the third place. A saved .kal or .fpcal is a file on disk. It becomes the running calibration only after an upload. FlashPro separates two upload targets: storing the file on the device, and writing it to the ECU.

Before storing a calibration on FlashPro, lock the device to the vehicle and register it. Use Online, then Lock to Vehicle, with the device connected to the car. Storing primary or secondary still leaves a separate ECU write to do.

Use the button sequence above with the ignition on and engine stopped, and wait for programming to finish before disconnecting anything.

Start with the ECU, not the engine size. Record the ECU code or suffix and the KPro generation if the board is visible in the software. Then record the engine and head, the cams, the VTC gear, the throttle type, the MAP sensor, the injector part number and the fuel pressure.

For a swap, record the chassis and the wiring separately from the ECU donor.

The ECU code gets you to a family, not to a finished calibration. A correct code does not prove the donor cams, throttle, intake, injectors or exhaust match. Those differences are why a base file needs a log before it earns trust.

1. Install the manager before the USB cable. Use the Windows application and the driver that ships with it. If Windows binds another driver first, the ECU may never appear as a Hondata device.
2. Connect with the ignition on and the engine off. KPro uses USB to the board. FlashPro uses the diagnostic port plus USB to the laptop. Check the status area before you open a table.
3. Stop if the device is not seen. Try a known USB cable, a different port and a powered laptop. Check ECU power and ground. Editing tables cannot fix an enumeration problem.
4. Check the sensors at key-on. MAP should sit near local ambient pressure, IAT and ECT should be plausible, and battery voltage should be steady. Check the closed-throttle reading and expected sensor travel with the engine stopped. On drive-by-wire, pedal and throttle channels need not show the same percentage. A wrong MAP scalar can make a fuel table look wrong later.
5. Record the versions. Write down the manager build, the device or board firmware, the ECU family and the calibration revision. KManager 4.6.5 is dated 6 October 2026. FlashProManager 4.7.7 is dated 9 September 2026. Those are release-history entries checked for this page.

KManager's New Calibration list contains calibrations that were tested on vehicle setups, and the description column names the setup. FlashProManager's New Calibration asks for the vehicle model and type, then offers stock-equivalent and tuned files, with a wizard on some vehicles. In both programs, the base file is a donor configuration.

• Save the chosen calibration under a new name before the first edit. Then enter the injector data, the MAP transfer, the idle type, the VTEC and VTC hardware, the rev limits and the communications the swap needs. Do not disable every diagnostic function as a shortcut. Each disabled circuit is a decision that has to match the wiring.
• Upload the file, wait for the reported completion, and follow the ignition prompts. Save the exact revision that was uploaded. Outside active live tuning, a change in the editor has not reached the ECU until that upload finishes. After the first start, confirm the sensors again and check for error codes before you record anything.

• On KPro, use Download to read the current ECU calibration before you replace it. Save it under a unique revision name and keep a second, untouched copy. If the ECU has a password or a protected calibration, record that state and resolve it with the owner or tuner. Do not try to bypass it.
• On FlashPro, there is no general read of whatever calibration another device flashed. Online Download retrieves the last calibration stored on the FlashPro. That is useful when the same device wrote the car. It is not a recovery tool for a tune written elsewhere. Before you replace a customer file, save the .fpcal you were given and keep it with the car's identity.

KManager live tuning changes RAM, not the file on disk

In KManager, live tuning is a KPro4 feature. It covers selected fuel, ignition and cam-angle tables, not every parameter. Select the tables, upload the calibration, then edit. The changes are held in RAM. An ignition-off and on cycle keeps them, but removing battery power restores the values from the last uploaded calibration.

That is not the same as factory stock.

• When the session ends, deselect the live tables and upload the completed calibration again. Save the matching .kal on the laptop. A KPro car that changes behavior after battery service can have a live-tuning persistence problem, not a sudden need for a new fuel map.
• FlashPro has its own live-tuning history, including instant live tuning on the FK2, FK8, FL5 and DE5. Those FlashPro features are separate from the KPro4 RAM rules above. Do not copy the KManager steps onto a FlashPro and assume the same behavior.

Vehicle lock, device security and calibration permissions

• A standard FlashPro locks to one vehicle at a time. Its security password can require authorization when uploading to the device and prevent release from the current vehicle. Calibration permissions use a different password: they can hide tables or restrict a file to a particular FlashPro serial number. A lost calibration-permissions password cannot be retrieved through the device-password reset.
• For a used unit, connect it to FlashProManager, open the FlashPro window and FlashPro tab, then expand License and Security. Check that the VIN status is unlocked and the Security Password is unset. Have the current owner resolve either restriction before purchase. Returning to stock and releasing the vehicle lock use the software; deleting an .fpcal does neither.

• FlashProManager separates watching from recording. F10 opens Datalog and shows sensor values, error codes and table tracing when a calibration is loaded. Those values are not saved. F9 starts Record, and a recording can be saved to disk. If you only used F10, you have no log to review.
• KManager can log to the laptop while connected. Later KPro boards can also log to onboard memory. Only boards with a serial number of 4111 or higher have that onboard function. The rate runs from 5 to 50 Hz on KPro, and KPro4 supports 100 Hz. A lower rate records longer, a higher rate resolves shorter events.

FlashPro's onboard recording time is listed as about 7.5 hours at the Fast rate and 21 hours at the Slow rate. The trade is resolution against duration. Do not promise a longer session from a headline memory size. Set the rate for the event you need to see.

Retrieve onboard logs before clearing memory

For KPro, open the KPro window's Datalogging tab. Download opens a selected recording in KManager; Save As downloads it straight to disk. Reopen the saved .kdl before using Delete All, because KPro does not delete recordings individually. Laptop and onboard logging cannot run together. With automatic onboard logging, both start conditions, rpm and throttle, must be met; recording stops when both stop conditions, rpm and vehicle speed, are met.

• For FlashPro, connect the unit to the computer, open the FlashPro window and select the recording, then use Download or the right-click menu. Save it as an .fpdl before deleting the device copy. Export only after the intended recording is loaded.
• For example, 5 Hz gives one sample every 0.20 seconds. At 50 Hz the interval is 0.020 seconds; at 100 Hz it is 0.010 seconds. A 0.10-second event spans less than one interval at 5 Hz, so a slow recording can miss it. These are sampling intervals, not a promise that every sensor updates that quickly.
• KManager and FlashProManager both record frames. A frame is a snapshot of the sensor set at one point in time. In KManager, the frame count and duration sit below the menu bar, and some sensors are not logged when the engine is not running. A key-on recording is not a substitute for a running log.

• The native log is the master. KManager's Export Datalog writes the current log to a comma-separated file. In FlashProManager, load the native log first, then use Datalog, then Export. There is no extra CSV submenu to find. If Export is unavailable, first check that a native log is loaded.
• A CSV is a one-way analysis export. No supported path was found that loads a CSV back as a .kdl or .fpdl. Keep the native file, the CSV and the calibration revision together. The native playback keeps the software context; the CSV is what an outside tool can open.

• Current KManager uses the .kal extension. SManager and s300 files are a different product family and stay outside this page.
• Hondata's KManager help lists the fields and units for Export Datalog. The help page spells short-term trim shorterm. Actual headers and extra channels can differ by version. Preserve the original header and create aliases in the analyzer; do not force a real file to match this baseline list.

FlashPro's changelog says datalog export uses regional settings. Treat the export as locale-dependent and inspect the decimal mark, the delimiter and the header before import. Using a comma as the import separator when the file uses decimal commas can split numeric values into extra columns.

• The KManager map export field is absolute pressure in bar. At 1.013 bar ambient, a 1.8 bar absolute reading is 0.787 bar above ambient, or about 11.4 psi of boost. Multiplying 1.8 by 14.5038 gives 26.1 psi absolute, not 26.1 psi of boost. Read the pressure reference before you describe the number.
• For a temperature check, a KManager tw value of 90 means 90°C, or 90 × 9 / 5 + 32 = 194°F. It is the same temperature as a 194°F native display. Do not change coolant settings because an export and a gauge use different units.
• Leave an absent channel marked as missing. Do not fill it with zero or derive it from an unrelated sensor. If the native playback does not have it, the export cannot invent it. Check whether the application and logging setup support that channel before recording again. If they do not, state that this log cannot answer the question.

A calibration and a log are a pair. Open the native log, confirm its duration, frame count, rpm and temperatures, then export the CSV and compare the same timestamp in both. If values disagree after unit conversion, check that the export and playback belong to the same recording and timestamp.

Do not tune from the mismatch.

1. Reopen the native log. Confirm that it is the session you think it is. Check duration and the first and last frame.
2. Export and reopen the CSV. Check the header, units and decimal mark. Compare one timestamp against native playback.
3. Match the calibration revision. The file name and notes should tie the log to the calibration revision that was in the ECU for that session.
4. Save the set under one name. Calibration, native log and CSV share a base name with the date and the change.
5. Remove personal identity before sharing. Do not publish a VIN, a customer name or a file path that contains either.

The logging guide covers channel-by-channel reading once the export is sound.