Commit tune maps and research so tunes are reachable from the phone

Removes the *.hex/maps_cache gitignore rule (explicit user call, reversing
the earlier no-redistribution stance) so the official TuneECU catalogue
maps, derived SAI/O2-delete composites, and the checksum/composition
tooling are actually available to pull up on a phone browser when using
the real TuneECU app. Also folds in tonight's KWP2000 fixes (TesterPresent
keep-alive, connect-failure cleanup, slow-init StartCommunication fix) and
the accumulated research docs.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01FP2GaxS9HkUdL5sLBnjKje

tunie/logs/tunie-bt-reset-20260826-201049.txt

@@ -0,0 +1,7 @@
+$ /opt/homebrew/bin/blueutil --disconnect 04-25-E8-5B-03-75
+$ /opt/homebrew/bin/blueutil --connect 04-25-E8-5B-03-75
+$ /opt/homebrew/bin/blueutil --info 04-25-E8-5B-03-75
+address: 04-25-e8-5b-03-75, not connected, not favourite, not paired, name: "04:25:E8:5B:03:75", recent access date: 2026-08-27 01:10:58 +0000
+
+NOT connected after reset
+(full session log: logs/tunie-bt-reset-20260826-201049.txt)

tunie/logs/tunie-bt-reset-20260826-201213.txt

@@ -0,0 +1,7 @@
+$ /opt/homebrew/bin/blueutil --disconnect 04-25-E8-5B-03-75
+$ /opt/homebrew/bin/blueutil --connect 04-25-E8-5B-03-75
+$ /opt/homebrew/bin/blueutil --info 04-25-E8-5B-03-75
+address: 04-25-e8-5b-03-75, not connected, not favourite, not paired, name: "04:25:E8:5B:03:75", recent access date: 2026-08-27 01:12:25 +0000
+
+NOT connected after reset
+(full session log: logs/tunie-bt-reset-20260826-201213.txt)

tunie/logs/tunie-bt-reset-20260826-201312.txt

@@ -0,0 +1,7 @@
+$ /opt/homebrew/bin/blueutil --disconnect 04-25-E8-5B-03-75
+$ /opt/homebrew/bin/blueutil --connect 04-25-E8-5B-03-75
+$ /opt/homebrew/bin/blueutil --info 04-25-E8-5B-03-75
+address: 04-25-e8-5b-03-75, not connected, not favourite, not paired, name: "04:25:E8:5B:03:75", recent access date: 2026-08-27 01:13:21 +0000
+
+NOT connected after reset
+(full session log: logs/tunie-bt-reset-20260826-201312.txt)

tunie/logs/tunie-info-20260822-142022.txt

@@ -0,0 +1,15 @@
+Connecting on /dev/cu.usbserial-A50285BI via kline, target 0xD5 source 0xF5, fast init...
+Attempt 1/3 failed (timed out waiting for 1 bytes, got 0 (none)); retrying in 5s...
+Attempt 2/3 failed (timed out waiting for 1 bytes, got 0 (none)); retrying in 5s...
+
+Connection failed after 3 attempt(s): timed out waiting for 1 bytes, got 0 (none)
+
+Things to check, in order:
+  1. Ignition on, engine off. The ECU sleeps otherwise.
+  2. Diagnostic connector pinout -- confirm before suspecting anything else.
+  3. Try --init slow (5-baud) if fast init times out.
+  4. If retries didn't help, the ignition may need a real power cycle --
+     turn it off, wait a few seconds, back on, and re-run.
+  5. On an ELM327 clone, KWP support is often broken; try the KKL cable.
+
+(full session log: logs/tunie-info-20260822-142022.txt)

tunie/logs/tunie-info-20260822-142121.txt

@@ -0,0 +1,15 @@
+Connecting on /dev/cu.usbserial-A50285BI via kline, target 0xD5 source 0xF5, slow init...
+Attempt 1/3 failed (5-baud init: expected sync byte 0x55, got 00); retrying in 5s...
+Attempt 2/3 failed (5-baud init: expected sync byte 0x55, got 00); retrying in 5s...
+
+Connection failed after 3 attempt(s): 5-baud init: expected sync byte 0x55, got 00
+
+Things to check, in order:
+  1. Ignition on, engine off. The ECU sleeps otherwise.
+  2. Diagnostic connector pinout -- confirm before suspecting anything else.
+  3. Try --init slow (5-baud) if fast init times out.
+  4. If retries didn't help, the ignition may need a real power cycle --
+     turn it off, wait a few seconds, back on, and re-run.
+  5. On an ELM327 clone, KWP support is often broken; try the KKL cable.
+
+(full session log: logs/tunie-info-20260822-142121.txt)

tunie/logs/tunie-info-20260822-142255.txt

@@ -0,0 +1,15 @@
+Connecting on /dev/cu.usbserial-A50285BI via kline, target 0xD5 source 0xF5, slow init...
+Attempt 1/3 failed (5-baud init: expected sync byte 0x55, got 00); retrying in 5s...
+Attempt 2/3 failed (5-baud init: expected sync byte 0x55, got 00); retrying in 5s...
+
+Connection failed after 3 attempt(s): 5-baud init: expected sync byte 0x55, got 00
+
+Things to check, in order:
+  1. Ignition on, engine off. The ECU sleeps otherwise.
+  2. Diagnostic connector pinout -- confirm before suspecting anything else.
+  3. Try --init slow (5-baud) if fast init times out.
+  4. If retries didn't help, the ignition may need a real power cycle --
+     turn it off, wait a few seconds, back on, and re-run.
+  5. On an ELM327 clone, KWP support is often broken; try the KKL cable.
+
+(full session log: logs/tunie-info-20260822-142255.txt)

tunie/logs/tunie-info-20260822-142356.txt

@@ -0,0 +1,15 @@
+Connecting on /dev/cu.usbserial-A50285BI via kline, target 0xD5 source 0xF5, slow init...
+Attempt 1/3 failed (5-baud init: expected sync byte 0x55, got 00); retrying in 5s...
+Attempt 2/3 failed (5-baud init: expected sync byte 0x55, got 00); retrying in 5s...
+
+Connection failed after 3 attempt(s): 5-baud init: expected sync byte 0x55, got 00
+
+Things to check, in order:
+  1. Ignition on, engine off. The ECU sleeps otherwise.
+  2. Diagnostic connector pinout -- confirm before suspecting anything else.
+  3. Try --init slow (5-baud) if fast init times out.
+  4. If retries didn't help, the ignition may need a real power cycle --
+     turn it off, wait a few seconds, back on, and re-run.
+  5. On an ELM327 clone, KWP support is often broken; try the KKL cable.
+
+(full session log: logs/tunie-info-20260822-142356.txt)

tunie/logs/tunie-info-20260822-142418.txt

@@ -0,0 +1,15 @@
+Connecting on /dev/cu.usbserial-A50285BI via kline, target 0xD5 source 0xF5, fast init...
+Attempt 1/3 failed (timed out waiting for 1 bytes, got 0 (none)); retrying in 5s...
+Attempt 2/3 failed (timed out waiting for 1 bytes, got 0 (none)); retrying in 5s...
+
+Connection failed after 3 attempt(s): timed out waiting for 1 bytes, got 0 (none)
+
+Things to check, in order:
+  1. Ignition on, engine off. The ECU sleeps otherwise.
+  2. Diagnostic connector pinout -- confirm before suspecting anything else.
+  3. Try --init slow (5-baud) if fast init times out.
+  4. If retries didn't help, the ignition may need a real power cycle --
+     turn it off, wait a few seconds, back on, and re-run.
+  5. On an ELM327 clone, KWP support is often broken; try the KKL cable.
+
+(full session log: logs/tunie-info-20260822-142418.txt)

tunie/logs/tunie-info-20260826-175905.txt

@@ -0,0 +1,11 @@
+Connecting on /dev/cu.vLinkerMC via kline, target 0xD5 source 0xF5, fast init...
+
+Connection failed: timed out waiting for 5 bytes, got 0 (none)
+
+Things to check, in order:
+  1. Ignition on, engine off. The ECU sleeps otherwise.
+  2. Diagnostic connector pinout -- confirm before suspecting anything else.
+  3. Try --init slow (5-baud) if fast init times out.
+  4. On an ELM327 clone, KWP support is often broken; try the KKL cable.
+
+(full session log: logs/tunie-info-20260826-175905.txt)

tunie/logs/tunie-info-20260826-175915.txt

@@ -0,0 +1,11 @@
+Connecting on /dev/cu.vLinkerMC via kline, target 0xD5 source 0xF5, slow init...
+
+Connection failed: timed out waiting for 1 bytes, got 0 (none)
+
+Things to check, in order:
+  1. Ignition on, engine off. The ECU sleeps otherwise.
+  2. Diagnostic connector pinout -- confirm before suspecting anything else.
+  3. Try --init slow (5-baud) if fast init times out.
+  4. On an ELM327 clone, KWP support is often broken; try the KKL cable.
+
+(full session log: logs/tunie-info-20260826-175915.txt)

tunie/logs/tunie-info-20260826-182538.txt

@@ -0,0 +1,11 @@
+Connecting on /dev/cu.vLinkerMC via elm327, target 0xD5 source 0xF5, slow init...
+
+Connection failed: adapter did not return a prompt for 'ATZ'; partial: ''
+
+Things to check, in order:
+  1. Ignition on, engine off. The ECU sleeps otherwise.
+  2. Diagnostic connector pinout -- confirm before suspecting anything else.
+  3. Try --init slow (5-baud) if fast init times out.
+  4. On an ELM327 clone, KWP support is often broken; try the KKL cable.
+
+(full session log: logs/tunie-info-20260826-182538.txt)

tunie/logs/tunie-info-20260826-182555.txt

@@ -0,0 +1,11 @@
+Connecting on /dev/cu.vLinkerMC via elm327, target 0xD5 source 0xF5, slow init...
+
+Connection failed: adapter did not return a prompt for 'ATZ'; partial: ''
+
+Things to check, in order:
+  1. Ignition on, engine off. The ECU sleeps otherwise.
+  2. Diagnostic connector pinout -- confirm before suspecting anything else.
+  3. Try --init slow (5-baud) if fast init times out.
+  4. On an ELM327 clone, KWP support is often broken; try the KKL cable.
+
+(full session log: logs/tunie-info-20260826-182555.txt)

tunie/logs/tunie-info-20260826-182636.txt

@@ -0,0 +1,11 @@
+Connecting on /dev/cu.vLinkerMC via elm327, target 0xD5 source 0xF5, fast init...
+
+Connection failed: adapter did not return a prompt for 'ATZ'; partial: ''
+
+Things to check, in order:
+  1. Ignition on, engine off. The ECU sleeps otherwise.
+  2. Diagnostic connector pinout -- confirm before suspecting anything else.
+  3. Try --init slow (5-baud) if fast init times out.
+  4. On an ELM327 clone, KWP support is often broken; try the KKL cable.
+
+(full session log: logs/tunie-info-20260826-182636.txt)

tunie/logs/tunie-info-20260826-182702.txt

@@ -0,0 +1,11 @@
+Connecting on /dev/cu.vLinkerMC via elm327, target 0xD5 source 0xF5, fast init...
+
+Connection failed: adapter did not return a prompt for 'ATZ'; partial: ''
+
+Things to check, in order:
+  1. Ignition on, engine off. The ECU sleeps otherwise.
+  2. Diagnostic connector pinout -- confirm before suspecting anything else.
+  3. Try --init slow (5-baud) if fast init times out.
+  4. On an ELM327 clone, KWP support is often broken; try the KKL cable.
+
+(full session log: logs/tunie-info-20260826-182702.txt)

tunie/logs/tunie-info-20260826-182721.txt

@@ -0,0 +1,11 @@
+Connecting on /dev/cu.vLinkerMC via elm327, target 0xD5 source 0xF5, fast init...
+
+Connection failed: adapter did not return a prompt for 'ATZ'; partial: ''
+
+Things to check, in order:
+  1. Ignition on, engine off. The ECU sleeps otherwise.
+  2. Diagnostic connector pinout -- confirm before suspecting anything else.
+  3. Try --init slow (5-baud) if fast init times out.
+  4. On an ELM327 clone, KWP support is often broken; try the KKL cable.
+
+(full session log: logs/tunie-info-20260826-182721.txt)

tunie/logs/tunie-info-20260826-193147.txt

@@ -0,0 +1,17 @@
+Connecting on /dev/cu.vLinkerMC via elm327, target 0xD5 source 0xF5, fast init...
+Attempt 1/5 failed (adapter did not return a prompt for 'ATZ'; partial: ''); retrying in 5s...
+Attempt 2/5 failed (adapter did not return a prompt for 'ATZ'; partial: ''); retrying in 5s...
+Attempt 3/5 failed (adapter did not return a prompt for 'ATZ'; partial: ''); retrying in 5s...
+Attempt 4/5 failed (adapter did not return a prompt for 'ATZ'; partial: ''); retrying in 5s...
+
+Connection failed after 5 attempt(s): adapter did not return a prompt for 'ATZ'; partial: ''
+
+Things to check, in order:
+  1. Ignition on, engine off. The ECU sleeps otherwise.
+  2. Diagnostic connector pinout -- confirm before suspecting anything else.
+  3. Try --init slow (5-baud) if fast init times out.
+  4. If retries didn't help, the ignition may need a real power cycle --
+     turn it off, wait a few seconds, back on, and re-run.
+  5. On an ELM327 clone, KWP support is often broken; try the KKL cable.
+
+(full session log: logs/tunie-info-20260826-193147.txt)

tunie/logs/tunie-info-20260826-193324.txt

@@ -0,0 +1,2 @@
+Connecting on /dev/cu.vLinkerMC via elm327, target 0xD5 source 0xF5, fast init...
+Attempt 1/5 failed (adapter did not return a prompt for 'ATZ'; partial: ''); retrying in 5s...

tunie/logs/tunie-info-20260826-193336.txt

@@ -0,0 +1,11 @@
+Connecting on /dev/cu.vLinkerMC via elm327, target 0xD5 source 0xF5, fast init...
+
+Connection failed: adapter did not return a prompt for 'ATZ'; partial: ''
+
+Things to check, in order:
+  1. Ignition on, engine off. The ECU sleeps otherwise.
+  2. Diagnostic connector pinout -- confirm before suspecting anything else.
+  3. Try --init slow (5-baud) if fast init times out.
+  4. On an ELM327 clone, KWP support is often broken; try the KKL cable.
+
+(full session log: logs/tunie-info-20260826-193336.txt)

tunie/logs/tunie-info-20260826-194806.txt

@@ -0,0 +1,2 @@
+Connecting on /dev/cu.vLinkerMC via elm327, target 0xD5 source 0xF5, fast init...
+Attempt 1/5 failed (adapter did not return a prompt for 'ATZ'; partial: ''); retrying in 5s...

tunie/logs/tunie-info-20260826-195018.txt

@@ -0,0 +1,13 @@
+Connecting on /dev/cu.vLinkerMC via elm327, target 0xD5 source 0xF5, fast init...
+
+Connection failed after 1 attempt(s): no hex payload in adapter response: 'BUS INIT: ERROR'
+
+Things to check, in order:
+  1. Ignition on, engine off. The ECU sleeps otherwise.
+  2. Diagnostic connector pinout -- confirm before suspecting anything else.
+  3. Try --init slow (5-baud) if fast init times out.
+  4. If retries didn't help, the ignition may need a real power cycle --
+     turn it off, wait a few seconds, back on, and re-run.
+  5. On an ELM327 clone, KWP support is often broken; try the KKL cable.
+
+(full session log: logs/tunie-info-20260826-195018.txt)

tunie/logs/tunie-info-20260826-195049.txt

@@ -0,0 +1,13 @@
+Connecting on /dev/cu.vLinkerMC via elm327, target 0xD5 source 0xF5, fast init...
+
+Connection failed after 1 attempt(s): adapter did not return a prompt for 'ATZ'; partial: ''
+
+Things to check, in order:
+  1. Ignition on, engine off. The ECU sleeps otherwise.
+  2. Diagnostic connector pinout -- confirm before suspecting anything else.
+  3. Try --init slow (5-baud) if fast init times out.
+  4. If retries didn't help, the ignition may need a real power cycle --
+     turn it off, wait a few seconds, back on, and re-run.
+  5. On an ELM327 clone, KWP support is often broken; try the KKL cable.
+
+(full session log: logs/tunie-info-20260826-195049.txt)

tunie/logs/tunie-info-20260826-195142.txt

@@ -0,0 +1,13 @@
+Connecting on /dev/cu.vLinkerMC via elm327, target 0xD5 source 0xF5, slow init...
+
+Connection failed after 1 attempt(s): adapter did not return a prompt for 'ATZ'; partial: ''
+
+Things to check, in order:
+  1. Ignition on, engine off. The ECU sleeps otherwise.
+  2. Diagnostic connector pinout -- confirm before suspecting anything else.
+  3. Try --init slow (5-baud) if fast init times out.
+  4. If retries didn't help, the ignition may need a real power cycle --
+     turn it off, wait a few seconds, back on, and re-run.
+  5. On an ELM327 clone, KWP support is often broken; try the KKL cable.
+
+(full session log: logs/tunie-info-20260826-195142.txt)

tunie/logs/tunie-info-20260826-195225.txt

@@ -0,0 +1 @@
+Connecting on /dev/cu.vLinkerMC via elm327, target 0xD5 source 0xF5, slow init...

tunie/logs/tunie-info-20260826-195246.txt

@@ -0,0 +1,13 @@
+Connecting on /dev/cu.vLinkerMC via elm327, target 0xD5 source 0xF5, slow init...
+
+Connection failed after 1 attempt(s): adapter did not return a prompt for 'ATZ'; partial: ''
+
+Things to check, in order:
+  1. Ignition on, engine off. The ECU sleeps otherwise.
+  2. Diagnostic connector pinout -- confirm before suspecting anything else.
+  3. Try --init slow (5-baud) if fast init times out.
+  4. If retries didn't help, the ignition may need a real power cycle --
+     turn it off, wait a few seconds, back on, and re-run.
+  5. On an ELM327 clone, KWP support is often broken; try the KKL cable.
+
+(full session log: logs/tunie-info-20260826-195246.txt)

tunie/logs/tunie-info-20260826-195326.txt

@@ -0,0 +1,13 @@
+Connecting on /dev/cu.vLinkerMC via elm327, target 0xD5 source 0xF5, slow init...
+
+Connection failed after 1 attempt(s): adapter did not return a prompt for 'ATZ'; partial: ''
+
+Things to check, in order:
+  1. Ignition on, engine off. The ECU sleeps otherwise.
+  2. Diagnostic connector pinout -- confirm before suspecting anything else.
+  3. Try --init slow (5-baud) if fast init times out.
+  4. If retries didn't help, the ignition may need a real power cycle --
+     turn it off, wait a few seconds, back on, and re-run.
+  5. On an ELM327 clone, KWP support is often broken; try the KKL cable.
+
+(full session log: logs/tunie-info-20260826-195326.txt)

tunie/logs/tunie-info-20260826-195512.txt

@@ -0,0 +1,13 @@
+Connecting on /dev/cu.vLinkerMC via elm327, target 0xD5 source 0xF5, slow init...
+
+Connection failed after 1 attempt(s): adapter reported 'BUS INIT: ...OK\rNO DATA' for 81
+
+Things to check, in order:
+  1. Ignition on, engine off. The ECU sleeps otherwise.
+  2. Diagnostic connector pinout -- confirm before suspecting anything else.
+  3. Try --init slow (5-baud) if fast init times out.
+  4. If retries didn't help, the ignition may need a real power cycle --
+     turn it off, wait a few seconds, back on, and re-run.
+  5. On an ELM327 clone, KWP support is often broken; try the KKL cable.
+
+(full session log: logs/tunie-info-20260826-195512.txt)

tunie/logs/tunie-info-20260826-195601.txt

@@ -0,0 +1,13 @@
+Connecting on /dev/cu.vLinkerMC via elm327, target 0xD5 source 0xF5, slow init...
+
+Connection failed after 1 attempt(s): adapter did not return a prompt for 'ATZ'; partial: ''
+
+Things to check, in order:
+  1. Ignition on, engine off. The ECU sleeps otherwise.
+  2. Diagnostic connector pinout -- confirm before suspecting anything else.
+  3. Try --init slow (5-baud) if fast init times out.
+  4. If retries didn't help, the ignition may need a real power cycle --
+     turn it off, wait a few seconds, back on, and re-run.
+  5. On an ELM327 clone, KWP support is often broken; try the KKL cable.
+
+(full session log: logs/tunie-info-20260826-195601.txt)

tunie/logs/tunie-info-20260826-200513.txt

@@ -0,0 +1,38 @@
+Connecting on /dev/cu.vLinkerMC via elm327, target 0xD5 source 0xF5, slow init...
+
+
+Diagnostic trouble codes: none reported
+
+Queries that did not answer
+  ReadEcuIdentification 0x80: adapter did not return a prompt for '1A80'; partial: 'BUS INIT: ...'
+  ReadEcuIdentification 0x81: no hex payload in adapter response: 'STOPPED'
+  ReadEcuIdentification 0x86: adapter did not return a prompt for '1A86'; partial: 'BUS INIT: ...'
+  ReadEcuIdentification 0x87: no hex payload in adapter response: 'STOPPED'
+  ReadEcuIdentification 0x88: adapter did not return a prompt for '1A88'; partial: 'BUS INIT: ...'
+  ReadEcuIdentification 0x89: no hex payload in adapter response: 'STOPPED'
+  ReadEcuIdentification 0x8A: adapter did not return a prompt for '1A8A'; partial: 'BUS INIT: ...'
+  ReadEcuIdentification 0x90: no hex payload in adapter response: 'STOPPED'
+  ReadEcuIdentification 0x91: adapter did not return a prompt for '1A91'; partial: 'BUS INIT: ...'
+  ReadEcuIdentification 0x92: no hex payload in adapter response: 'STOPPED'
+  ReadEcuIdentification 0x93: adapter did not return a prompt for '1A93'; partial: 'BUS INIT: ...'
+  ReadEcuIdentification 0x94: no hex payload in adapter response: 'STOPPED'
+  ReadEcuIdentification 0x95: adapter did not return a prompt for '1A95'; partial: 'BUS INIT: ...'
+  ReadEcuIdentification 0x96: no hex payload in adapter response: 'STOPPED'
+  ReadEcuIdentification 0x97: adapter did not return a prompt for '1A97'; partial: 'BUS INIT: ...'
+  ReadEcuIdentification 0x98: no hex payload in adapter response: 'STOPPED'
+  ReadEcuIdentification 0x99: adapter did not return a prompt for '1A99'; partial: 'BUS INIT: ...'
+  ReadEcuIdentification 0x9A: no hex payload in adapter response: 'STOPPED'
+  ReadEcuIdentification 0x9B: adapter did not return a prompt for '1A9B'; partial: 'BUS INIT: ...'
+  ReadEcuIdentification 0x9C: no hex payload in adapter response: 'STOPPED'
+  ReadDataByLocalIdentifier 0x80: adapter did not return a prompt for '2180'; partial: 'BUS INIT: ...'
+  ReadDataByLocalIdentifier 0x81: no hex payload in adapter response: 'STOPPED'
+  ReadDataByLocalIdentifier 0x00: adapter did not return a prompt for '2100'; partial: 'BUS INIT: ...'
+  ReadDataByLocalIdentifier 0x01: no hex payload in adapter response: 'STOPPED'
+  ReadDataByLocalIdentifier 0x02: adapter did not return a prompt for '2102'; partial: 'BUS INIT: ...'
+  ReadDataByLocalIdentifier 0x03: no hex payload in adapter response: 'STOPPED'
+  ReadDataByLocalIdentifier 0x10: adapter did not return a prompt for '2110'; partial: 'BUS INIT: ...'
+  ReadDataByLocalIdentifier 0x11: no hex payload in adapter response: 'STOPPED'
+  ReadDtcByStatus 0x18: adapter did not return a prompt for '1800FF00'; partial: 'BUS INIT: ...'
+  ReadDtc 0x13: adapter did not return a prompt for '1340FF'; partial: 'BUS INIT: ...'
+
+(full session log: logs/tunie-info-20260826-200513.txt)

tunie/logs/tunie-info-20260826-200812.txt

@@ -0,0 +1,13 @@
+Connecting on /dev/cu.vLinkerMC via elm327, target 0xD5 source 0xF5, slow init...
+
+Connection failed after 1 attempt(s): adapter did not return a prompt for 'ATZ'; partial: ''
+
+Things to check, in order:
+  1. Ignition on, engine off. The ECU sleeps otherwise.
+  2. Diagnostic connector pinout -- confirm before suspecting anything else.
+  3. Try --init slow (5-baud) if fast init times out.
+  4. If retries didn't help, the ignition may need a real power cycle --
+     turn it off, wait a few seconds, back on, and re-run.
+  5. On an ELM327 clone, KWP support is often broken; try the KKL cable.
+
+(full session log: logs/tunie-info-20260826-200812.txt)

tunie/logs/tunie-info-20260826-200906.txt

@@ -0,0 +1,13 @@
+Connecting on /dev/cu.vLinkerMC via elm327, target 0xD5 source 0xF5, slow init...
+
+Connection failed after 1 attempt(s): adapter did not return a prompt for 'ATZ'; partial: ''
+
+Things to check, in order:
+  1. Ignition on, engine off. The ECU sleeps otherwise.
+  2. Diagnostic connector pinout -- confirm before suspecting anything else.
+  3. Try --init slow (5-baud) if fast init times out.
+  4. If retries didn't help, the ignition may need a real power cycle --
+     turn it off, wait a few seconds, back on, and re-run.
+  5. On an ELM327 clone, KWP support is often broken; try the KKL cable.
+
+(full session log: logs/tunie-info-20260826-200906.txt)

tunie/logs/tunie-info-20260826-201108.txt

@@ -0,0 +1,13 @@
+Connecting on /dev/cu.vLinkerMC via elm327, target 0xD5 source 0xF5, slow init...
+
+Connection failed after 1 attempt(s): could not open /dev/cu.vLinkerMC: [Errno 2] could not open port /dev/cu.vLinkerMC: [Errno 2] No such file or directory: '/dev/cu.vLinkerMC'
+
+Things to check, in order:
+  1. Ignition on, engine off. The ECU sleeps otherwise.
+  2. Diagnostic connector pinout -- confirm before suspecting anything else.
+  3. Try --init slow (5-baud) if fast init times out.
+  4. If retries didn't help, the ignition may need a real power cycle --
+     turn it off, wait a few seconds, back on, and re-run.
+  5. On an ELM327 clone, KWP support is often broken; try the KKL cable.
+
+(full session log: logs/tunie-info-20260826-201108.txt)

tunie/logs/tunie-info-20260826-201432.txt

@@ -0,0 +1,38 @@
+Connecting on /dev/cu.vLinkerMC via elm327, target 0xD5 source 0xF5, slow init...
+
+
+Diagnostic trouble codes: none reported
+
+Queries that did not answer
+  ReadEcuIdentification 0x80: no hex payload in adapter response: '.STOPPED'
+  ReadEcuIdentification 0x81: no hex payload in adapter response: '.STOPPED'
+  ReadEcuIdentification 0x86: no hex payload in adapter response: 'STOPPED'
+  ReadEcuIdentification 0x87: no hex payload in adapter response: 'STOPPED'
+  ReadEcuIdentification 0x88: no hex payload in adapter response: 'STOPPED'
+  ReadEcuIdentification 0x89: no hex payload in adapter response: 'STOPPED'
+  ReadEcuIdentification 0x8A: no hex payload in adapter response: 'STOPPED'
+  ReadEcuIdentification 0x90: no hex payload in adapter response: 'STOPPED'
+  ReadEcuIdentification 0x91: no hex payload in adapter response: 'STOPPED'
+  ReadEcuIdentification 0x92: no hex payload in adapter response: 'STOPPED'
+  ReadEcuIdentification 0x93: no hex payload in adapter response: 'STOPPED'
+  ReadEcuIdentification 0x94: no hex payload in adapter response: 'STOPPED'
+  ReadEcuIdentification 0x95: no hex payload in adapter response: 'STOPPED'
+  ReadEcuIdentification 0x96: no hex payload in adapter response: 'STOPPED'
+  ReadEcuIdentification 0x97: no hex payload in adapter response: 'STOPPED'
+  ReadEcuIdentification 0x98: no hex payload in adapter response: 'STOPPED'
+  ReadEcuIdentification 0x99: no hex payload in adapter response: 'STOPPED'
+  ReadEcuIdentification 0x9A: no hex payload in adapter response: 'STOPPED'
+  ReadEcuIdentification 0x9B: no hex payload in adapter response: 'STOPPED'
+  ReadEcuIdentification 0x9C: no hex payload in adapter response: 'STOPPED'
+  ReadDataByLocalIdentifier 0x80: no hex payload in adapter response: 'STOPPED'
+  ReadDataByLocalIdentifier 0x81: no hex payload in adapter response: 'STOPPED'
+  ReadDataByLocalIdentifier 0x00: no hex payload in adapter response: 'STOPPED'
+  ReadDataByLocalIdentifier 0x01: no hex payload in adapter response: 'STOPPED'
+  ReadDataByLocalIdentifier 0x02: no hex payload in adapter response: 'STOPPED'
+  ReadDataByLocalIdentifier 0x03: no hex payload in adapter response: 'STOPPED'
+  ReadDataByLocalIdentifier 0x10: no hex payload in adapter response: 'STOPPED'
+  ReadDataByLocalIdentifier 0x11: no hex payload in adapter response: 'STOPPED'
+  ReadDtcByStatus 0x18: adapter did not return a prompt for '1800FF00'; partial: 'BUS INIT: ...'
+  ReadDtc 0x13: adapter did not return a prompt for '1340FF'; partial: 'BUS INIT: ...'
+
+(full session log: logs/tunie-info-20260826-201432.txt)

tunie/logs/tunie-info-20260826-201831.txt

@@ -0,0 +1,13 @@
+Connecting on /dev/cu.vLinkerMC via elm327, target 0xD5 source 0xF5, slow init...
+
+Connection failed after 1 attempt(s): adapter did not return a prompt for 'ATZ'; partial: ''
+
+Things to check, in order:
+  1. Ignition on, engine off. The ECU sleeps otherwise.
+  2. Diagnostic connector pinout -- confirm before suspecting anything else.
+  3. Try --init slow (5-baud) if fast init times out.
+  4. If retries didn't help, the ignition may need a real power cycle --
+     turn it off, wait a few seconds, back on, and re-run.
+  5. On an ELM327 clone, KWP support is often broken; try the KKL cable.
+
+(full session log: logs/tunie-info-20260826-201831.txt)

tunie/logs/tunie-info-20260826-201947.txt

@@ -0,0 +1,13 @@
+Connecting on /dev/cu.vLinkerMC via elm327, target 0xD5 source 0xF5, slow init...
+
+Connection failed after 1 attempt(s): could not open /dev/cu.vLinkerMC: [Errno 2] could not open port /dev/cu.vLinkerMC: [Errno 2] No such file or directory: '/dev/cu.vLinkerMC'
+
+Things to check, in order:
+  1. Ignition on, engine off. The ECU sleeps otherwise.
+  2. Diagnostic connector pinout -- confirm before suspecting anything else.
+  3. Try --init slow (5-baud) if fast init times out.
+  4. If retries didn't help, the ignition may need a real power cycle --
+     turn it off, wait a few seconds, back on, and re-run.
+  5. On an ELM327 clone, KWP support is often broken; try the KKL cable.
+
+(full session log: logs/tunie-info-20260826-201947.txt)

tunie/logs/tunie-info-20260826-202004.txt

@@ -0,0 +1,38 @@
+Connecting on /dev/cu.vLinkerMC via elm327, target 0xD5 source 0xF5, slow init...
+
+
+Diagnostic trouble codes: none reported
+
+Queries that did not answer
+  ReadEcuIdentification 0x80: no hex payload in adapter response: 'STOPPED'
+  ReadEcuIdentification 0x81: no hex payload in adapter response: 'STOPPED'
+  ReadEcuIdentification 0x86: no hex payload in adapter response: '.STOPPED'
+  ReadEcuIdentification 0x87: no hex payload in adapter response: 'STOPPED'
+  ReadEcuIdentification 0x88: no hex payload in adapter response: 'STOPPED'
+  ReadEcuIdentification 0x89: no hex payload in adapter response: 'STOPPED'
+  ReadEcuIdentification 0x8A: no hex payload in adapter response: 'STOPPED'
+  ReadEcuIdentification 0x90: no hex payload in adapter response: 'STOPPED'
+  ReadEcuIdentification 0x91: no hex payload in adapter response: 'STOPPED'
+  ReadEcuIdentification 0x92: no hex payload in adapter response: 'STOPPED'
+  ReadEcuIdentification 0x93: no hex payload in adapter response: 'STOPPED'
+  ReadEcuIdentification 0x94: no hex payload in adapter response: 'STOPPED'
+  ReadEcuIdentification 0x95: no hex payload in adapter response: 'STOPPED'
+  ReadEcuIdentification 0x96: no hex payload in adapter response: 'STOPPED'
+  ReadEcuIdentification 0x97: no hex payload in adapter response: 'STOPPED'
+  ReadEcuIdentification 0x98: no hex payload in adapter response: 'STOPPED'
+  ReadEcuIdentification 0x99: no hex payload in adapter response: 'STOPPED'
+  ReadEcuIdentification 0x9A: no hex payload in adapter response: 'STOPPED'
+  ReadEcuIdentification 0x9B: no hex payload in adapter response: 'STOPPED'
+  ReadEcuIdentification 0x9C: no hex payload in adapter response: 'STOPPED'
+  ReadDataByLocalIdentifier 0x80: no hex payload in adapter response: 'STOPPED'
+  ReadDataByLocalIdentifier 0x81: no hex payload in adapter response: 'STOPPED'
+  ReadDataByLocalIdentifier 0x00: no hex payload in adapter response: 'STOPPED'
+  ReadDataByLocalIdentifier 0x01: no hex payload in adapter response: 'STOPPED'
+  ReadDataByLocalIdentifier 0x02: no hex payload in adapter response: 'STOPPED'
+  ReadDataByLocalIdentifier 0x03: no hex payload in adapter response: 'STOPPED'
+  ReadDataByLocalIdentifier 0x10: no hex payload in adapter response: 'STOPPED'
+  ReadDataByLocalIdentifier 0x11: no hex payload in adapter response: 'STOPPED'
+  ReadDtcByStatus 0x18: adapter did not return a prompt for '1800FF00'; partial: 'BUS INIT: ...'
+  ReadDtc 0x13: adapter did not return a prompt for '1340FF'; partial: 'BUS INIT: ...'
+
+(full session log: logs/tunie-info-20260826-202004.txt)

tunie/logs/tunie-info-20260826-202342.txt

@@ -0,0 +1,13 @@
+Connecting on /dev/cu.vLinkerMC via elm327, target 0xD5 source 0xF5, slow init...
+
+Connection failed after 1 attempt(s): adapter did not return a prompt for 'ATZ'; partial: ''
+
+Things to check, in order:
+  1. Ignition on, engine off. The ECU sleeps otherwise.
+  2. Diagnostic connector pinout -- confirm before suspecting anything else.
+  3. Try --init slow (5-baud) if fast init times out.
+  4. If retries didn't help, the ignition may need a real power cycle --
+     turn it off, wait a few seconds, back on, and re-run.
+  5. On an ELM327 clone, KWP support is often broken; try the KKL cable.
+
+(full session log: logs/tunie-info-20260826-202342.txt)

tunie/logs/tunie-info-20260826-202430.txt

@@ -0,0 +1 @@
+Connecting on /dev/cu.vLinkerMC via elm327, target 0xD5 source 0xF5, fast init...

tunie/logs/tunie-info-20260826-202609.txt

@@ -0,0 +1,13 @@
+Connecting on /dev/cu.vLinkerMC via elm327, target 0xD5 source 0xF5, fast init...
+
+Connection failed after 1 attempt(s): adapter did not return a prompt for 'ATZ'; partial: ''
+
+Things to check, in order:
+  1. Ignition on, engine off. The ECU sleeps otherwise.
+  2. Diagnostic connector pinout -- confirm before suspecting anything else.
+  3. Try --init slow (5-baud) if fast init times out.
+  4. If retries didn't help, the ignition may need a real power cycle --
+     turn it off, wait a few seconds, back on, and re-run.
+  5. On an ELM327 clone, KWP support is often broken; try the KKL cable.
+
+(full session log: logs/tunie-info-20260826-202609.txt)

tunie/logs/tunie-info-20260826-202735.txt

@@ -0,0 +1,13 @@
+Connecting on /dev/cu.vLinkerMC via elm327, target 0xD5 source 0xF5, fast init...
+
+Connection failed after 1 attempt(s): adapter did not return a prompt for 'ATZ'; partial: ''
+
+Things to check, in order:
+  1. Ignition on, engine off. The ECU sleeps otherwise.
+  2. Diagnostic connector pinout -- confirm before suspecting anything else.
+  3. Try --init slow (5-baud) if fast init times out.
+  4. If retries didn't help, the ignition may need a real power cycle --
+     turn it off, wait a few seconds, back on, and re-run.
+  5. On an ELM327 clone, KWP support is often broken; try the KKL cable.
+
+(full session log: logs/tunie-info-20260826-202735.txt)

tunie/logs/tunie-info-20260826-202801.txt

@@ -0,0 +1,13 @@
+Connecting on /dev/cu.vLinkerMC via elm327, target 0xD5 source 0xF5, slow init...
+
+Connection failed after 1 attempt(s): adapter did not return a prompt for 'ATZ'; partial: ''
+
+Things to check, in order:
+  1. Ignition on, engine off. The ECU sleeps otherwise.
+  2. Diagnostic connector pinout -- confirm before suspecting anything else.
+  3. Try --init slow (5-baud) if fast init times out.
+  4. If retries didn't help, the ignition may need a real power cycle --
+     turn it off, wait a few seconds, back on, and re-run.
+  5. On an ELM327 clone, KWP support is often broken; try the KKL cable.
+
+(full session log: logs/tunie-info-20260826-202801.txt)

tunie/logs/tunie-info-20260826-202922.txt

@@ -0,0 +1,13 @@
+Connecting on /dev/cu.vLinkerMC via elm327, target 0xD5 source 0xF5, fast init...
+
+Connection failed after 1 attempt(s): could not open /dev/cu.vLinkerMC: [Errno 2] could not open port /dev/cu.vLinkerMC: [Errno 2] No such file or directory: '/dev/cu.vLinkerMC'
+
+Things to check, in order:
+  1. Ignition on, engine off. The ECU sleeps otherwise.
+  2. Diagnostic connector pinout -- confirm before suspecting anything else.
+  3. Try --init slow (5-baud) if fast init times out.
+  4. If retries didn't help, the ignition may need a real power cycle --
+     turn it off, wait a few seconds, back on, and re-run.
+  5. On an ELM327 clone, KWP support is often broken; try the KKL cable.
+
+(full session log: logs/tunie-info-20260826-202922.txt)

tunie/logs/tunie-info-20260826-202926.txt

@@ -0,0 +1,13 @@
+Connecting on /dev/cu.vLinkerMC via elm327, target 0xD5 source 0xF5, fast init...
+
+Connection failed after 1 attempt(s): could not open /dev/cu.vLinkerMC: [Errno 2] could not open port /dev/cu.vLinkerMC: [Errno 2] No such file or directory: '/dev/cu.vLinkerMC'
+
+Things to check, in order:
+  1. Ignition on, engine off. The ECU sleeps otherwise.
+  2. Diagnostic connector pinout -- confirm before suspecting anything else.
+  3. Try --init slow (5-baud) if fast init times out.
+  4. If retries didn't help, the ignition may need a real power cycle --
+     turn it off, wait a few seconds, back on, and re-run.
+  5. On an ELM327 clone, KWP support is often broken; try the KKL cable.
+
+(full session log: logs/tunie-info-20260826-202926.txt)

tunie/logs/tunie-info-20260826-202947.txt

@@ -0,0 +1,13 @@
+Connecting on /dev/cu.vLinkerMC via elm327, target 0xD5 source 0xF5, fast init...
+
+Connection failed after 1 attempt(s): no hex payload in adapter response: 'BUS INIT: ERROR'
+
+Things to check, in order:
+  1. Ignition on, engine off. The ECU sleeps otherwise.
+  2. Diagnostic connector pinout -- confirm before suspecting anything else.
+  3. Try --init slow (5-baud) if fast init times out.
+  4. If retries didn't help, the ignition may need a real power cycle --
+     turn it off, wait a few seconds, back on, and re-run.
+  5. On an ELM327 clone, KWP support is often broken; try the KKL cable.
+
+(full session log: logs/tunie-info-20260826-202947.txt)

tunie/logs/tunie-info-20260826-203035.txt

@@ -0,0 +1,13 @@
+Connecting on /dev/cu.vLinkerMC via elm327, target 0xD5 source 0xF5, slow init...
+
+Connection failed after 1 attempt(s): adapter did not return a prompt for 'ATZ'; partial: ''
+
+Things to check, in order:
+  1. Ignition on, engine off. The ECU sleeps otherwise.
+  2. Diagnostic connector pinout -- confirm before suspecting anything else.
+  3. Try --init slow (5-baud) if fast init times out.
+  4. If retries didn't help, the ignition may need a real power cycle --
+     turn it off, wait a few seconds, back on, and re-run.
+  5. On an ELM327 clone, KWP support is often broken; try the KKL cable.
+
+(full session log: logs/tunie-info-20260826-203035.txt)

tunie/logs/tunie-info-20260826-214932.txt

@@ -0,0 +1,13 @@
+Connecting on /dev/cu.usbserial-A50285BI via kline, target 0xD5 source 0xF5, slow init...
+
+Connection failed after 1 attempt(s): 5-baud init: expected sync byte 0x55, got 00
+
+Things to check, in order:
+  1. Ignition on, engine off. The ECU sleeps otherwise.
+  2. Diagnostic connector pinout -- confirm before suspecting anything else.
+  3. Try --init slow (5-baud) if fast init times out.
+  4. If retries didn't help, the ignition may need a real power cycle --
+     turn it off, wait a few seconds, back on, and re-run.
+  5. On an ELM327 clone, KWP support is often broken; try the KKL cable.
+
+(full session log: logs/tunie-info-20260826-214932.txt)

tunie/logs/tunie-info-20260826-214948.txt

@@ -0,0 +1,3 @@
+Connecting on /dev/cu.usbserial-A50285BI via kline, target 0xD5 source 0xF5, fast init...
+Attempt 1/3 failed (timed out waiting for 1 bytes, got 0 (none)); retrying in 5s...
+Attempt 2/3 failed (timed out waiting for 1 bytes, got 0 (none)); retrying in 5s...

tunie/logs/tunie-info-20260826-215009.txt

@@ -0,0 +1,2 @@
+Connecting on /dev/cu.usbserial-A50285BI via kline, target 0xD5 source 0xF5, slow init...
+Attempt 1/3 failed (5-baud init: expected sync byte 0x55, got 00); retrying in 5s...

tunie/logs/tunie-info-20260826-215023.txt

@@ -0,0 +1,3 @@
+Connecting on /dev/cu.usbserial-A50285BI via kline, target 0xD5 source 0xF5, slow init...
+Attempt 1/3 failed (5-baud init: expected sync byte 0x55, got 00); retrying in 5s...
+Attempt 2/3 failed (5-baud init: expected sync byte 0x55, got 00); retrying in 5s...

tunie/logs/tunie-raw-20260826-183647.txt

@@ -0,0 +1,2 @@
+Opening /dev/cu.doesnotexist @ 38400 baud (settle 2.0s)...
+could not open /dev/cu.doesnotexist: [Errno 2] could not open port /dev/cu.doesnotexist: [Errno 2] No such file or directory: '/dev/cu.doesnotexist'

tunie/logs/tunie-raw-20260826-192719.txt

@@ -0,0 +1,7 @@
+Opening /dev/cu.vLinkerMC @ 38400 baud (settle 2.0s)...
+-> b'ATZ\r'
+<- nothing received in 5.0s
+
+This means the adapter itself never answered -- the problem is upstream of tunie (the OS<->adapter serial/Bluetooth channel), not in tunie's protocol handling. Re-pairing the adapter (forget it in Bluetooth settings, pair fresh) is the next thing to try, not a tunie flag.
+
+(full session log: logs/tunie-raw-20260826-192719.txt)

tunie/logs/tunie-raw-20260826-192743.txt

@@ -0,0 +1,7 @@
+Opening /dev/cu.vLinkerMC @ 38400 baud (settle 2.0s)...
+-> b'ATZ\r'
+<- nothing received in 5.0s
+
+This means the adapter itself never answered -- the problem is upstream of tunie (the OS<->adapter serial/Bluetooth channel), not in tunie's protocol handling. Re-pairing the adapter (forget it in Bluetooth settings, pair fresh) is the next thing to try, not a tunie flag.
+
+(full session log: logs/tunie-raw-20260826-192743.txt)

tunie/logs/tunie-raw-20260826-192837.txt

@@ -0,0 +1,7 @@
+Opening /dev/cu.vLinkerMC @ 38400 baud (settle 2.0s)...
+-> b'ATZ\r'
+<- nothing received in 5.0s
+
+This means the adapter itself never answered -- the problem is upstream of tunie (the OS<->adapter serial/Bluetooth channel), not in tunie's protocol handling. Re-pairing the adapter (forget it in Bluetooth settings, pair fresh) is the next thing to try, not a tunie flag.
+
+(full session log: logs/tunie-raw-20260826-192837.txt)

tunie/logs/tunie-raw-20260826-193133.txt

@@ -0,0 +1,9 @@
+Opening /dev/cu.vLinkerMC @ 38400 baud (settle 2.0s)...
+-> b'ATZ\r'
+<- 20 bytes:
+   hex   : 41 54 5a 0d 0d 0d 45 4c 4d 33 32 37 20 76 32 2e 32 0d 0d 3e
+   ascii : 'ATZ\r\r\rELM327 v2.2\r\r>'
+
+Something answered -- the link is alive. If this was an ELM327 adapter and the response doesn't look like an ELM327 banner/prompt, the issue is likely in how tunie is talking to it, not the link itself.
+
+(full session log: logs/tunie-raw-20260826-193133.txt)

tunie/logs/tunie-raw-20260826-202441.txt

@@ -0,0 +1,7 @@
+Opening /dev/cu.vLinkerMC @ 38400 baud (settle 2.0s)...
+-> b'ATZ\r'
+<- nothing received in 5.0s
+
+This means the adapter itself never answered -- the problem is upstream of tunie (the OS<->adapter serial/Bluetooth channel), not in tunie's protocol handling. Re-pairing the adapter (forget it in Bluetooth settings, pair fresh) is the next thing to try, not a tunie flag.
+
+(full session log: logs/tunie-raw-20260826-202441.txt)

tunie/logs/tunie-raw-20260826-202721.txt

@@ -0,0 +1,9 @@
+Opening /dev/cu.vLinkerMC @ 38400 baud (settle 2.0s)...
+-> b'ATZ\r'
+<- 20 bytes:
+   hex   : 41 54 5a 0d 0d 0d 45 4c 4d 33 32 37 20 76 32 2e 32 0d 0d 3e
+   ascii : 'ATZ\r\r\rELM327 v2.2\r\r>'
+
+Something answered -- the link is alive. If this was an ELM327 adapter and the response doesn't look like an ELM327 banner/prompt, the issue is likely in how tunie is talking to it, not the link itself.
+
+(full session log: logs/tunie-raw-20260826-202721.txt)

tunie/logs/tunie-raw-20260826-214846.txt

@@ -0,0 +1,9 @@
+Opening /dev/cu.usbserial-A50285BI @ 10400 baud (settle 2.0s)...
+-> b'ATZ\r'
+<- 4 bytes:
+   hex   : 41 54 5a 0d
+   ascii : 'ATZ\r'
+
+Exact echo of what was sent -- for a raw K-Line (KKL/FTDI) adapter this IS the expected good result: it means the wire, transceiver, and pinout are electrically sound (K-Line is half-duplex -- your own bytes always come back). It does NOT mean the ECU answered anything; only a real KWP2000 exchange (tunie info --adapter kline) exercises that.
+
+(full session log: logs/tunie-raw-20260826-214846.txt)

tunie/logs/tunie-raw-20260826-214859.txt

@@ -0,0 +1,9 @@
+Opening /dev/cu.usbserial-A50285BI @ 10400 baud (settle 2.0s)...
+-> b'ATZ\r'
+<- 4 bytes:
+   hex   : 41 54 5a 0d
+   ascii : 'ATZ\r'
+
+Exact echo of what was sent -- for a raw K-Line (KKL/FTDI) adapter this IS the expected good result: it means the wire, transceiver, and pinout are electrically sound (K-Line is half-duplex -- your own bytes always come back). It does NOT mean the ECU answered anything; only a real KWP2000 exchange (tunie info --adapter kline) exercises that.
+
+(full session log: logs/tunie-raw-20260826-214859.txt)

tunie/logs/tunie-raw-20260826-220407.txt

@@ -0,0 +1,2 @@
+Opening /dev/cu.usbserial-A50285BI @ 10400 baud (settle 2.0s)...
+could not open /dev/cu.usbserial-A50285BI: [Errno 2] could not open port /dev/cu.usbserial-A50285BI: [Errno 2] No such file or directory: '/dev/cu.usbserial-A50285BI'