Use Case Documentation - gmenounos/kw1281test GitHub Wiki
Disclaimer: This documentation was written by Anthropic's Claude AI on September 19, 2026, based on a review of community forum discussion. It may contain omissions or errors β verify anything safety- or cost-relevant against your own testing before relying on it.
This is a task-oriented companion to the Command Reference wiki page, the authoritative syntax reference for kw1281test. Where the Command Reference tells you what each command does, this guide shows real, worked examples of the jobs people actually use the tool for β extracted from years of community troubleshooting on the TDIClub kw1281test thread.
All examples below reflect the tool's current command set and syntax. Remember that the ADDRESS argument is always parsed as hex (so 46 means controller address 0x46, not decimal 46 β see the Command Reference's Controller address table), and that START/LENGTH/ADDRESS (memory)/VALUE arguments accept decimal, 0xβ¦, or $β¦ interchangeably.
β οΈ Anything that writes to a module (WriteEeprom,LoadEeprom,AdaptationSave,SetSoftwareCoding,WriteEdc15Eeprom,WriteRAM) can disable a feature, break a key/immobilizer pairing, or leave a module non-functional if interrupted or given a wrong value. Always dump the affected range first so you have a backup, and never interrupt a write mid-way (battery disconnect is usually the only recovery).
- 1. Getting started
- 2. Getting the immobilizer SKC
- 3. Programming keys and fobs
- 4. CCM / comfort-convenience mods
- 5. Cluster customization
- 6. VIN correction and ECU pairing
- 7. Fault codes and diagnostics
- 8. Radio SAFE codes
- 9. EDC15 ECU operations
- 10. Troubleshooting and known limitations
kw1281test COMx 10400 17 ReadIdent
Always run this first on any module you haven't worked with before. It returns the part number and a description (e.g. 1J5920926CX KOMBI+WEGFAHRSP VDO V01), which tells you the manufacturer (VDO, Marelli, Bosch/Motometer) β and that decides which of the commands in this guide will actually work on it.
Some vehicles (e.g. certain Seat Alhambra/VW Sharan models) keep the immobilizer in its own module rather than inside the cluster. Check both before troubleshooting a failed GetSKC:
kw1281test COMx 10400 17 ReadIdent REM cluster
kw1281test COMx 10400 25 ReadIdent REM dedicated immobilizer box, if present
If GetSKC against 17 fails with "Unable to find Immobilizer ID in cluster dump" but ReadIdent on 25 returns a valid response, target 25 instead for SKC/adaptation work.
- A cheap USBβKKL cable works fine on Windows with either an FTDI or CH340 chipset. On macOS/Linux you need an FTDI-chipped cable β CH340's timing isn't precise enough for the 5-baud wakeup handshake kw1281test relies on.
- A genuine Ross-Tech VCDS cable (older HEX-CAN/HEX-USB/serial) can be used if switched into Virtual COM Port (VCP) mode via Ross-Tech's own driver utility. HEX-NET and HEX-V2 do not support this and cannot be used with kw1281test.
- On macOS/Linux, the
PORTargument isn'tCOMxβ it's the FTDI cable's serial number (see the Command Reference's Ports and cables section), e.g.:./kw1281test AB5P37BA 10400 17 ReadIdent - The tool is a console app β run it from an actual terminal/PowerShell/Command Prompt window (
cdto the folder first, or.\kw1281test.exein PowerShell), not by double-clicking the.exe. - In PowerShell, escape a leading
$in hex arguments with a backtick (`$CC), or just use decimal/0xnotation instead to sidestep the issue entirely.
If a DumpEeprom/LoadEeprom/GetSKC call times out on the first try, run ReadIdent (or ReadSoftwareVersion on a VDO cluster) against the same module first β this often "wakes it up" and makes the next command succeed. Occasional timeouts are normal on some hardware/cable combinations; just retry.
Take a full EEPROM dump before any risky edit (CCM mod, SKC work, needle sweep, etc.) so you can restore it if something goes wrong:
kw1281test COMx 10400 17 DumpEeprom 0 2048 backup.bin
kw1281test COMx 10400 17 LoadEeprom 0 backup.bin
(2048 bytes is standard for a VDO Immo2/Immo3 MKIV cluster; other cluster families use different sizes β see Β§2.6.) Verify you have a good dump file before ever writing one back.
The SKC (Super Key Code) is the 5-digit immobilizer code needed to adapt keys. GetSKC is the modern, recommended way to retrieve it and works differently depending on what ReadIdent reports the module as β but the manual fallback methods below remain useful when a specific cluster revision isn't recognized.
kw1281test COMx 10400 17 GetSKC REM cluster
kw1281test COMx 10400 25 GetSKC REM immobilizer box (see 1.2)
kw1281test COMx 9600 1 GetSKC REM engine ECU (Bosch EDC15 only)
If the cluster's specific software version isn't yet in the tool's internal lookup table, it reports the raw unlock code and asks you to report it to the maintainer β worth doing, since it usually gets added to the next release.
kw1281test COMx 10400 17 DumpEeprom 204 6
Returns 3 identical repeating byte-pairs, e.g. 07 0B 07 0B 07 0B. Decode: take one pair, flip the byte order, convert hexβdecimal, zero-pad to 5 digits.
Example: bytes D3 1F β flip β 1FD3 (hex) β 8147 (decimal) β SKC 08147.
The SKC offset varies by cluster firmware β if 204 doesn't return a sensible repeating pattern, try 266:
kw1281test COMx 10400 17 DumpEeprom 266 6
(Confirmed needed for BEW-engined clusters and some R32 clusters β check ReadSoftwareVersion if unsure which firmware you have.)
Immo2 stores the SKC as a 2-byte pair, redundantly, at three separate locations:
kw1281test COMx 10400 17 DumpEeprom 186 2
kw1281test COMx 10400 17 DumpEeprom 202 2
kw1281test COMx 10400 17 DumpEeprom 218 2
Decode: reverse the byte order and read directly as decimal (not hex-weighted like Immo3), e.g. 02 21 β SKC 2102. In practice the three copies don't always agree β if one location gives a working SKC and the others don't, trust the one that worked.
RB4 clusters run encrypted by default, which blocks a plain SKC read. Toggle to New Mode, read the SKC, then toggle back:
kw1281test COMx 10400 17 ToggleRB4Mode
kw1281test COMx 10400 17 GetSKC
kw1281test COMx 10400 17 ToggleRB4Mode
kw1281test COMx 10400 17 DumpRBxMem 66560 1024
These clusters are picky about parameters β using any address/length other than the values shown can lock the cluster up until you disconnect the battery or unplug it.
kw1281test COMx 10400 17 GetSKC
GetSKC recognizes Marelli (M73) clusters directly and computes the SKC from an internal EEPROM dump β try this first for any Beetle or Audi TT cluster. If it reports the cluster as unrecognized, fall back to a manual dump β the correct start address/length depends on the cluster generation, so try both:
kw1281test COMx 9600 17 DumpMarelliMem 3072 1024 REM earlier Immo2-era Marelli clusters
kw1281test COMx 9600 17 DumpMarelliMem 14336 2048 REM later Immo3-era Marelli clusters
If DumpMarelliMem itself fails with "unsupported cluster software version," fall back to a raw DumpEeprom at addresses taken from the cluster's own microcontroller datasheet, e.g.:
kw1281test COMx 9600 17 DumpEeprom 0 4096
kw1281test COMx 9600 17 DumpEeprom 16384 49152
This will require manually inspecting the dump (e.g. in a hex editor) for the SKC pattern, since automatic decoding won't apply. Marelli EEPROM writing is not supported β these procedures are read-only.
kw1281test COMx 9600 1 GetSKC
Only Bosch EDC15 ECUs support this (not EDC16 β see Β§10.5); only Immo3-era ECUs actually carry their own SKC (Immo2-era cars keep it in the cluster only). If you get a timeout, disconnect the battery (or pull the ECU fuse) to force a reboot before retrying.
With the new key in the ignition, turned to "On" (engine off):
kw1281test COMx 10400 17 AdaptationSave 21 1 <SKC>
The immobilizer light should flash then go out. Remove the key, wait ~30 seconds, then try starting the car.
AdaptationSave sets the total number of registered keys β any key not re-registered as part of the same operation stops working (though its transponder chip is unaffected and can be re-included any time by repeating the process with it present). To add a key without losing old ones:
kw1281test COMx 9600 17 AdaptationSave 21 <total-key-count> <SKC>
Step by step:
- Insert the new key, turn to "On" β immobilizer light comes on.
- Run the command above, with
<total-key-count>= old keys + the new one. - Immobilizer light turns off once adaptation succeeds.
- Remove the new key, insert an existing key, turn to "On" β the immobilizer light should blink once then go out (it's now been re-registered as part of the batch).
- Repeat step 4 for each additional existing key you want to keep working.
Separate from key/immobilizer adaptation β this teaches the CCM to recognize a fob's RF signal:
kw1281test COMx 9600 46 AdaptationSave 0 0 REM clears existing fob-related CCM settings
kw1281test COMx 9600 46 AdaptationSave 1 1 REM channel 1 = number of fobs to register
Within ~30 seconds of the second command, press and hold the fob's unlock button for about 1 second until the horn honks, confirming it's registered. To program more than one fob, increase the value (not the channel), e.g. AdaptationSave 1 2 for two fobs.
AdaptationTest applies a value live so you can observe the effect, without permanently saving it:
kw1281test COMx 9600 46 AdaptationRead 1 REM check the current value first
kw1281test COMx 9600 46 AdaptationTest 1 2 REM preview channel 1 = value 2; does not persist
kw1281test COMx 9600 46 AdaptationSave 1 2 REM commit it for real once confirmed
A value reverting after AdaptationTest (rather than staying set) is expected β that's the difference between "test" and "save."
CCM address and bit layout differ by part number family β always confirm which family you have (via ReadIdent) before writing.
π Extended address reference: the VDS_pro Resource thread (TDIClub) maintains a much more extensive, community-compiled list of CCM addresses for the window-fob mod across many additional car/CCM variants than are practical to reproduce here β worth checking if your specific car isn't covered by the general 1C0/1J0 maps below. It also documents an important exception: on older (MK3-era) cars, the bit that controls remote window operation doesn't work the same way as the "clear bit 3" pattern described below for MK4-era 1C0/1J0 CCMs β see that thread for the MK3-specific procedure.
Read the current value at all three redundant copies, clear bit 3, write it back to all three:
kw1281test COMx 9600 46 ReadEeprom 04361
kw1281test COMx 9600 46 ReadEeprom 04362
kw1281test COMx 9600 46 ReadEeprom 04363
kw1281test COMx 9600 46 WriteEeprom 04361 130
kw1281test COMx 9600 46 WriteEeprom 04362 130
kw1281test COMx 9600 46 WriteEeprom 04363 130
(130 assumes a starting value of 138 with bit 3 cleared β always read your actual value first, since the correct target value depends on what other options are already coded.) This bit-3 pattern applies to MK4-era 1C0/1J0 CCMs; see the note above for older MK3-era cars.
7 config bytes, each stored redundantly at 3 addresses:
Byte 0: 04352, 04353, 04354
Byte 1: 04355, 04356, 04357
Byte 2: 04358, 04359, 04360
Byte 3: 04361, 04362, 04363
Byte 4: 04364, 04365, 04366
Byte 5: 04367, 04368, 04369
Byte 6: 04370, 04371, 04372
Dump them all at once for inspection:
kw1281test COMx 9600 46 DumpEeprom 04352 21
6 config bytes, redundantly stored at 3 addresses each (different layout than 1C0):
Byte 0: 04280, 04286, 04292
Byte 1: 04281, 04287, 04293
Byte 2: 04282, 04288, 04294
Byte 3: 04283, 04289, 04295
Byte 4: 04284, 04290, 04296
Byte 5: 04285, 04291, 04297
Dump them all:
kw1281test COMx 9600 46 DumpEeprom 04280 18
Example: enabling "unlock hatch with doors" on a 1J0 CCM means clearing bit 7 at addresses 04280/04286/04292 β always verify against your own read-back rather than assuming a value from another car's CCM.
4.4 Wagon: unlock the hatch (with no auto-relock timeout) whenever the car is unlocked β MK4 Passat/Jetta wagon only
Stock wagon behavior: the hatch stays locked even when the rest of the car is unlocked, unless explicitly unlocked via the remote's dedicated hatch button or by pulling up the switch in the driver's door β and even then, it re-locks itself after about a minute if not opened.
To change this so the hatch simply unlocks (with no timeout) whenever the car is unlocked, and re-locks when the car is locked, use the same procedure as the window-fob mod (Β§4.1) but set bit 0 instead of clearing bit 3:
kw1281test COMx 9600 46 ReadEeprom 04361
kw1281test COMx 9600 46 ReadEeprom 04362
kw1281test COMx 9600 46 ReadEeprom 04363
kw1281test COMx 9600 46 WriteEeprom 04361 <value with bit 0 set>
kw1281test COMx 9600 46 WriteEeprom 04362 <value with bit 0 set>
kw1281test COMx 9600 46 WriteEeprom 04363 <value with bit 0 set>
This mod is specific to MK4 Passat and Jetta wagons β it relies on hatch-lock wiring/logic that other body styles don't have.
Each window regulator motor on a 1C0-family CCM has its own EEPROM, addressable through the CCM at different offsets:
kw1281test COMx 9600 46 DumpEeprom 4096 512 REM CCM itself
kw1281test COMx 9600 46 DumpEeprom 8192 512 REM front-left window motor
kw1281test COMx 9600 46 DumpEeprom 12288 512 REM front-right window motor
kw1281test COMx 9600 46 DumpEeprom 16384 512 REM rear-left window motor
kw1281test COMx 9600 46 DumpEeprom 20480 512 REM rear-right window motor
This module answers at address 09, not 46:
kw1281test COMx 10400 09 ReadEeprom 61003
kw1281test COMx 10400 09 WriteEeprom 61003 <newvalue>
If ReadEeprom fails against this module but you know the target value from documentation, WriteEeprom to the same address has been reported to work anyway.
A car whose factory setup uses a plain central-locking module (rather than a full CCM) can accept a donor Beetle central-locking module (e.g. part 1C0962258AB) for remote locking, at address 35:
kw1281test COMx 9600 35 ReadEeprom 04361
kw1281test COMx 9600 35 WriteEeprom 04361 <value>
Its bit layout matches a 1C0959799 CCM once addressed correctly.
Dump the donor cluster, then load the (possibly edited) file onto the target cluster:
kw1281test COMx 10400 17 DumpEeprom 0 2048 donor.bin
kw1281test COMx 10400 17 LoadEeprom 0 donor.bin
kw1281test COMx 10400 17 Reset
This is how the community handles moving needle-sweep behavior, tachometer redline recalibration (e.g. for an engine swap), and gauge-face overlay changes between clusters β edit the donor dump in a hex editor before loading it, or load it as-is to make the target cluster behave exactly like the donor.
LoadEeprom doesn't require a full 2048-byte image β you can write a short patch starting at any address, which is how community cluster mods (like needle-sweep enablement for a specific firmware) are typically distributed:
kw1281test COMx 10400 17 LoadEeprom 0x4F4 NeedleSweep_VWK501MH_00A4.bin
kw1281test COMx 10400 17 Reset
Always reset (or fully power-cycle) the cluster afterward so it picks up the change β some option changes don't take effect until the connector is unplugged and reconnected, even after Reset.
Extracting your own patch region from a donor dump: if you want to pull just a specific address range out of a full EEPROM dump (e.g. to create a shareable patch file), remember LENGTH is inclusive of both endpoints β i.e. LENGTH = end_address - start_address + 1, not just the raw difference:
kw1281test COMx 10400 17 DumpEeprom 0x4F4 0x1A0 NeedleSweep_VWK501MH_00A4.bin
(Here, copying from 0x4F4 to 0x693 inclusive means length 0x693 - 0x4F4 + 1 = 0x1A0, not 0x19E.)
kw1281test COMx 9600 17 ActuatorTest
Cycles the cluster's gauges through an output-test sequence β the same function as VCDS's "Run Cluster Output Tests." Useful after reassembling a cluster or swapping needles to verify/re-align them. Press N to advance through actuators, Q to stop.
kw1281test COMx 10400 17 WriteEeprom 1047 107
(equivalently 0x0417/0x6B in hex β use one notation consistently to avoid mixing them up.)
Useful when swapping to a transmission that has no vehicle-speed sensor (e.g. an 02Jβ02S swap, where the 02S doesn't provide a speed signal the cluster can read directly) β recode the cluster to instead take vehicle speed from the ABS data already present on the CAN bus:
kw1281test COMx 10400 17 ReadSoftwareVersion REM confirm you have a VDO VWK501 or VWK503 cluster
kw1281test COMx 10400 17 ReadEeprom 0x65 REM check the current value (typically 0x80)
kw1281test COMx 10400 17 WriteEeprom 0x65 0x81 REM switch the speed source to ABS/CAN
kw1281test COMx 10400 17 ReadEeprom 0x65 REM confirm the write took (should now read 0x81)
Verify the speedometer works correctly with no transmission speed-sensor signal present. If 0x81 doesn't produce a working speedometer, try 0x82 instead and re-test β the exact value can vary by cluster software version, so confirm with a ReadSoftwareVersion first and adjust if the first attempt doesn't work.
Full procedure for a salvage-yard ECU and/or cluster still carrying a donor car's VIN (Immo3):
REM 1. Back up the cluster's full EEPROM
kw1281test COMx 10400 17 DumpEeprom 0 2048 oldvin.bin
REM 2. Edit oldvin.bin in a hex editor to correct the VIN bytes, save as newvin.bin
REM 3. Write the corrected EEPROM back to the cluster
kw1281test COMx 10400 17 LoadEeprom 0 newvin.bin
kw1281test COMx 10400 17 Reset
REM 4. Get the (now-corrected) cluster's SKC
kw1281test COMx 10400 17 GetSKC
REM 5. Re-pair the ECU to the cluster (channel 50; login = cluster SKC, value = ECU SKC)
REM If cluster and ECU share the same SKC (the common case):
kw1281test COMx 10400 1 AdaptationSave 50 01234 01234
REM If the ECU has a distinct SKC (e.g. an Immo-deleted donor ECU β get it first via GetSKC on address 1):
kw1281test COMx 10400 1 AdaptationSave 50 01234 05678
REM 6. Power-cycle: ignition off for 1 minute, then back on
REM 7. Verify the ECU now reports the correct VIN
kw1281test COMx 10400 1 ReadIdent
If only the ECU's VIN is wrong (cluster VIN is already correct), skip straight to step 5. To inspect an EDC15 ECU's own EEPROM (VIN, SKC, odometer) without changing anything, see Β§9.1.
The CAN Gateway (inside the cluster, address 19) needs to know which modules are actually installed in the car (transmission type, ABS, airbag, etc.):
kw1281test COMx 9600 19 SetSoftwareCoding <coding> <workshop>
Good practice after installing any "new" (used) cluster: re-save the coding even if it already looks correct β this makes the gateway re-scan the CAN bus, which often clears stale fault codes left over from the swap.
kw1281test COMx 9600 15 ReadFaultCodes REM airbag module example
kw1281test COMx 9600 15 ClearFaultCodes
Works on any addressable module, not just the cluster β common addresses: ECU 01, Central Electric 09, airbag 15, cluster 17, CAN Gateway 19, immobilizer box 25, central locking 35, CCM 46, radio 56.
kw1281test COMx 9600 1 ReadIdent REM confirm the connection first
kw1281test COMx 9600 1 BasicSetting 60
Channel 60 runs the throttle body alignment basic-setting routine; let it run for about 30 seconds before quitting.
For VW51, VW61, or 1C0909601 airbag controllers, a shorthand form of DumpEeprom dumps the whole EEPROM with the size auto-detected per controller type β no need to know the start address or length yourself:
kw1281test COMx 9600 15 DumpEeprom airbag.bin
(EEPROM sizes: VW51 = 512 bytes, VW61 = 768 bytes, 1C0909601 = 784 bytes, the last one unconfirmed as of this writing.) This is read-only guidance β a companion ClearCrashData command exists in the source but is currently disabled by the maintainer after it caused memory corruption on a VW51 controller, so don't expect it to be available yet.
kw1281test COMx 9600 56 ClarionVWPremium4SafeCode
The 2-byte response (e.g. 0x13 0x80) is read as a plain 4-digit code in the order received β do not hex-convert or byte-swap it (1380, not a converted/flipped value). If the radio shows "2 SAFE" after a failed attempt, it needs continuous power for roughly an hour before you can try again (VW's anti-brute-force lockout).
kw1281test COMx 9600 7C DelcoVWPremium5SafeCode
Any other OEM radio (other Clarion/Delco variants, Blaupunkt, Philips, etc.) will respond to ReadIdent but return nothing useful from either SAFE-code command. For those, a third-party VW-radio-code lookup service (using the radio's serial number) is the practical fallback.
These only work on Bosch EDC15 engine ECUs (address 01) β see Β§10.5 for EDC16.
kw1281test COMx 9600 1 DumpEdc15Eeprom rom.bin
Prints the SKC, VIN, odometer reading, immo ID, and whether the immobilizer is currently on or off, in addition to saving the raw 512-byte EEPROM to rom.bin.
kw1281test COMx 9600 1 WriteEdc15Eeprom 0x1B0 0x60 0x1DE 0x60
This writes the specific address/value pairs that disable the EDC15 immobilizer. A full EEPROM backup is taken automatically before the write. Treat this as high-risk β if the write is interrupted, disconnect the battery for a minute to reset the ECU; in the worst case the ECU can be left unresponsive.
Run ReadIdent against both address 17 and address 25 (see Β§1.2) β some vehicles keep the immobilizer in a separate module, and GetSKC needs to target the address that actually holds it.
Fall back to a raw DumpEeprom at addresses from the cluster's own microcontroller datasheet (see Β§2.6). Some individual cluster firmware revisions genuinely aren't supported yet, even after ruling out cable/driver/baud issues.
The same part number has, in different production runs, been built by different suppliers (VDO vs. Bosch) or in firmware sub-revisions with different memory layouts. Matching part number alone doesn't guarantee a given address/command will work β always check the ReadIdent software-version string too, and be prepared that some specific sub-revisions may simply be unsupported.
KW1281 has timing sensitivities that vary by cable/laptop combination; a timeout roughly 1 in 20β30 attempts on some hardware is not unusual. Just retry, or try Β§1.4's "wake it up first" trick.
kw1281test's ECU commands (GetSKC, DumpEdc15Eeprom, WriteEdc15Eeprom) only work against Bosch EDC15 ECUs. EDC16 ECUs use a different, unsupported protocol and fail immediately with a protocol error. If your car has an EDC16, get the SKC from the cluster instead:
kw1281test COMx 10400 17 GetSKC
Community members have built third-party graphical front-ends that call the same underlying executable and wrap common ReadEeprom/WriteEeprom/DumpEeprom/LoadEeprom operations behind buttons. These are independent projects β the command-line tool and the Command Reference remain the authoritative reference for available functionality.
Compiled from community troubleshooting on the TDIClub kw1281test thread. As with any EEPROM-editing tool, back up before you write, and proceed at your own risk.