Advisories
Conditions found in the field, with the change that resolves each one. Each advisory states the devices it affects, what causes it, what to do, and its current status.
An advisory stays here after it is fixed. Units already in service keep the old behaviour until they are updated or rewired, so a resolved advisory is still the answer for somebody. Every page carries the version a fix landed in, or says plainly that none has.
These are written in the first person because I wrote the firmware they describe.
Current advisories
Newest first.
| Published | Advisory | Affects | Status |
|---|---|---|---|
| 17 Oct 2024 | Startup time after power-up is not consistent | All devices — the bootloader, before any firmware version applies | Open — no fix recorded |
| 8 Oct 2024 | CAN messages sent at irregular intervals on busy networks | Firmware older than 2.0.1, on loaded networks | Resolved in 2.0.1 |
| 5 Oct 2024 | Fault in the valve control loop | Firmware older than 2.0.1, direct valve control only | Resolved in 2.0.1 |
| 5 Oct 2024 | Adaptation data lost when the supply drops with the ignition | Standalone transmission controller, any firmware, depending on how KL30 is wired | Open — wiring change is the fix |
Two of these are cleared by updating the firmware. If you are on anything older than 2.0.1 and chasing a communication problem or unexplained shift quality, update before you spend a weekend on the wiring.
If you are diagnosing something now
An advisory is a record of a known condition. If you do not already know which one you are looking at, start from the symptom instead:
- Troubleshooting — symptom to cause
- Fault codes — a code the device reported
- CAN bus diagnostics — communication problems
- Stated limitations — behaviour that is intended, not a fault