LibreTune - HaniCore K-line build 0.1.0-hanicore.5 (unofficial)

LibreTune — HaniCore K-line build 0.1.0-hanicore.5 (unofficial)

An unofficial build of LibreTune
with native K-line support for HaniCore
ECUs: an ordinary KKL / VAG-COM cable, on the ECU's K-line pin or in the car's
OBD socket. Not an official LibreTune release; report problems to HaniCore.

Source: LibreTune-HaniCore-0.1.0-hanicore.5-source.zip (the fork's
working tree, based on upstream a884bb1). What changed: FORK.md.

License: GPL-2.0 (LICENSE), as LibreTune; third-party notices in
THIRD_PARTY_NOTICES.md.

What is new since 0.1.0-hanicore.3

• Live graphs beside the settings, and faster live data (only the values on
  screen are read: 12-19 updates per second on a K-line).
• Data logging records the ECU's datalog channels.
• Based on upstream LibreTune a884bb1.
• Dashboard: right-click a gauge -> Replace Gauge -> category -> gauge.
  The list is the ECU file's own gauges (ignition timing, dwell, lambda, ...),
  grouped as in the .ini, and the choice is kept. Before, the list was a
  generic one whose gauges a HaniCore ECU does not have, and it appeared only
  in designer mode.

Use

1. Run LibreTune-HaniCore-0.1.0-hanicore.5.exe (portable, Windows x64, needs
   the WebView2 runtime that Windows 10/11 already has).
2. New project / Connect ECU -> K-line (KKL / VAG-COM cable) -> cable
   connected to ECU K-line pin or car OBD socket -> COM port -> 57600 ->
   Next. Import the board's .ini from the HaniCore release when asked.

Checksums

SHA256SUMS.

LibreTune - HaniCore K-line build 0.1.0-hanicore.3 (unofficial)

LibreTune — HaniCore K-line build 0.1.0-hanicore.3 (unofficial)

An unofficial build of LibreTune
with native K-line support for HaniCore
ECUs: an ordinary KKL / VAG-COM cable, on the ECU's K-line pin or in the car's
OBD socket. Not an official LibreTune release; report problems to HaniCore.

Source: tag v0.1.0-hanicore.3 of this repository (based on upstream
cc5cf23), also attached as LibreTune-HaniCore-0.1.0-hanicore.3-source.zip.
What changed: FORK.md and CHANGELOG.md.

License: GPL-2.0 (LICENSE), as LibreTune; third-party notices in
THIRD_PARTY_NOTICES.md.

What is new since 0.1.0-hanicore.1

• INI values use the TunerStudio rule (raw + translate) * scale - temperatures,
  the ignition map and sensor pickers read and wrote wrong before. Tunes saved by
  hanicore.1 are converted once on load.
• VE / ignition edits reach the ECU over K-line (writes in 64-byte frames, read back).
• The page is re-read when the ECU asks for it ([EventTriggers]): after automatic
  throttle calibration the PID values update on screen by themselves.
• Indicator lights, { ... } labels and readout panels work in the release build.
• New-project wizard: the board's own definition is matched by its board name, the
  last working port is offered, the baud rate used is the one stored, no stray
  Difference Report on a new project.
• The Burn window closes after a successful Burn and the project's tune is saved
  then. Window titles show the menu name only. The ? beside each setting shows
  the help text the INI carries.

Use

1. Run LibreTune-HaniCore-0.1.0-hanicore.3.exe (portable, Windows x64, needs the
   WebView2 runtime that Windows 10/11 already has). It keeps its own settings,
   apart from an official LibreTune install; projects in
   Documents\LibreTuneProjects are shared.
2. New project / Connect ECU -> K-line (KKL / VAG-COM cable) -> cable
   connected to ECU K-line pin or car OBD socket -> COM port -> 57600 ->
   Next. Import the board's .ini from the HaniCore release when asked for the
   ECU definition.

Tested

On HaniCore ECUs on the bench (FTDI KKL, direct 57600): Porsche ME7.1.1, ME7.5
4B0906018DC and Audi 2.7T 4B0907551F - new project from the wizard, every menu
opened, VE and ignition edits followed live, sensor picker + Burn + power cycle,
throttle AutoCal with the PID fields refreshing by themselves. Frontend tests
383/383.

Checksums

SHA256SUMS.

LibreTune - HaniCore K-line build 0.1.0-hanicore.1 (unofficial)

LibreTune — HaniCore K-line build 0.1.0-hanicore.1 (unofficial)

An unofficial build of LibreTune
with native K-line support for HaniCore
ECUs: an ordinary KKL / VAG-COM cable, on the ECU's K-line pin or in the car's
OBD socket. Not an official LibreTune release; report problems to HaniCore.

Source: tag v0.1.0-hanicore.1 of this repository (commit a1f3391,
based on upstream cc5cf23), also attached as
LibreTune-HaniCore-0.1.0-hanicore.1-source.zip. What changed: FORK.md.

License: GPL-2.0 (LICENSE), as LibreTune; third-party notices in
THIRD_PARTY_NOTICES.md.

Use

1. Run LibreTune-HaniCore-0.1.0-hanicore.1.exe (portable, Windows x64,
   needs the WebView2 runtime that Windows 10/11 already has). It keeps its
   own settings, apart from an official LibreTune install; projects in
   Documents\LibreTuneProjects are shared.
2. New project / Connect ECU → K-line (KKL / VAG-COM cable) → cable
   connected to ECU K-line pin or car OBD socket → COM port → 57600
   or 124800 → Next. Import the board's .ini from the HaniCore release when
   asked for the ECU definition.
3. Existing project: Connection → K-line → the same choices → Connect.

The connection recovers by itself after the ECU is power-cycled.

Tested

On a Porsche ME7.1.1 running HaniCore (bench, FTDI KKL): direct 57600 /
124800 and through the KWP entry at 124800 / 115200 — live data, table edit,
Burn, recovery after an ECU power cycle, page unchanged at the end. Unit
tests: the K-line channel against a simulated cable + ECU; LibreTune's own
suites pass (core 715, frontend 379).

Checksums

SHA256SUMS.