Tuning Wiki

BMW uses D-CAN for tester communication, K-CAN for body electronics and PT-CAN for powertrain communication. Check the platform and build date when identifying a network. BMW phased D-CAN in across models, and its training manual documents both 100 kbit/s K-CAN and 500 kbit/s K-CAN2 in different applications.

NetworkRole and examples
D-CAN500 kbit/s diagnostic interface. BMW identifies pins 6 and 14 as the CAN communication connections at the diagnostic socket. Depending on the ECU, diagnostic traffic can use KWP 2000 or UDS.
K-CAN and K-CAN2Body networks. BMW documents 100 kbit/s K-CAN and 500 kbit/s K-CAN2, including K-CAN2 on the F30.
PT-CANPowertrain network. See the BMW platform and CAN ID reference for platform-specific bit rates and signal layouts.

D-CAN diagnostic requests

These read-only request examples come from published bench research for the MK60E5 DSC controller with BMW job file DSC_87.prg. The tester request uses CAN ID 0x6F1 and the module replies on 0x629 in this setup. In the request data, 29 is the target address, followed by the ISO-TP single-frame length byte and the KWP 2000 service payload. Other modules and software versions can use different addresses and services.

BMW jobMeaningRequest data in hex, excluding padding
IDENTRead controller identification29 02 1A 80
FS_LESENRead stored fault codes29 04 18 02 FF FF

K-CAN broadcast example

The community E8x/E9x DBC labels CAN ID 0x19E (414 decimal) as StatusDSC_KCAN, an eight-byte status frame with signals for DSC and brake state, plus a counter and checksum. This is a broadcast to identify in a capture. The DBC documents a community decode, so confirm the layout against the platform and ECU in use.

Related references

Sources

The illustrated vehicle diagnostics protocol guide connects the vehicle networks, diagnostic services and scan-tool interfaces.